docs: merge Dev v3 into main #546
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose
This pull request introduces several important updates to deployment requirements, workflow configuration, and agent behavior, as well as a minor frontend style change. The most significant changes are the enforcement of a minimum Azure Developer CLI (azd) version, enhanced instructions and validation in deployment workflows, and stricter output formatting for retail agents.
Deployment requirements and documentation:
README.md
,docs/DeploymentGuide.md
) and theazure.yaml
configuration to require Azure Developer CLI (azd) version 1.18.0 or higher, replacing the previous minimum version and adding clear upgrade/download instructions. [1] [2] [3] [4]Workflow and security improvements:
.github/workflows/azure-dev.yml
) by adding a production environment, using secret-based credentials, enabling additional validation options, and improving output handling and documentation for each step.Agent behavior and compliance:
system_message
for bothCustomerDataAgent
andOrderDataAgent
indata/agent_teams/retail.json
, adding explicit instructions to avoid all forms of citations, source references, or attribution markers in responses, ensuring clean and compliant output. [1] [2]Frontend style adjustment:
.tab
class inTeamSelector.module.css
to use a negative margin, likely to refine tab alignment or spacing in the UI.Does this introduce a breaking change?
How to Test